WinSock - definizione. Che cos'è WinSock
Diclib.com
Dizionario ChatGPT
Inserisci una parola o una frase in qualsiasi lingua 👆
Lingua:

Traduzione e analisi delle parole tramite l'intelligenza artificiale ChatGPT

In questa pagina puoi ottenere un'analisi dettagliata di una parola o frase, prodotta utilizzando la migliore tecnologia di intelligenza artificiale fino ad oggi:

  • come viene usata la parola
  • frequenza di utilizzo
  • è usato più spesso nel discorso orale o scritto
  • opzioni di traduzione delle parole
  • esempi di utilizzo (varie frasi con traduzione)
  • etimologia

Cosa (chi) è WinSock - definizione

TECHNICAL SPECIFICATION FOR HOW WINDOWS SOFTWARE SHOULD BEHAVE OVER TCP/IP
Windows Sockets; Windows Sockets 2; Winsock client; WinSock; Windows sockets; Winsock Visual Basic; Ws2 32; Winsock2; Winsock 2; Winsock RIO extensions; Ws2 32.dll; Windows Socket API; Windows socket; Windows Sockets API; Windows Socket 2; Wsock.dll; Wsock32.dll

Winsock         
Winsock         
In computing, the Windows Sockets API (WSA), later shortened to Winsock, is an application programming interface (API) that defines how Windows network application software should access network services, especially TCP/IP. It defines a standard interface between a Windows TCP/IP client application (such as an FTP client or a web browser) and the underlying TCP/IP protocol stack.
Windows sockets         
<networking, standard> (Winsock) A specification for Microsoft Windows network software, describing how applications can access network services, especially TCP/IP. Winsock is intended to provide a single API to which application developers should program and to which multiple network software vendors should conform. For any particular version of Microsoft Windows, it defines a binary interface (ABI) such that an application written to the Windows Sockets API can work with a conformant protocol implementation from any network software vendor. Winsock was conceived at Fall Interop '91 during a {Birds of a Feather} session. Windows Sockets is supported by Microsoft Windows, {Windows for Workgroups}, Win32s, Windows 95 and Windows NT. It will support protocols other than TCP/IP. Under {Windows NT}, Microsoft will provide Windows Sockets support over TCP/IP and IPX/SPX. DEC will be implementing DECNet. Windows NT will include mechanisms for multiple protocol support in Windows Sockets, both 32-bit and 16 bit. Mark Towfiq said, "The next rev. of Winsock will not be until toward the end of 1993. We need 1.1 of the API to become firmly settled and implemented first." {winsock">Windows Sockets API (ftp://sunsite.unc.edu/pub/micro/pc-stuff/ms-windows/winsock)}. or winsock">ftp://microdyne.com/pub/winsock or send a message "help" to either <ftpmail@SunSite.UNC.Edu> or <ftpmail@DECWRL.DEC.Com>. Windows Sockets specification (ftp://rhino.microsoft.com). Currently NetManage (NEWT), Distinct, FTP and Frontier are shipping Winsock TCP/IP stacks, as is Microsoft (Windows NT and TCP/IP for WFW), Beame & Whiteside Software (v1.1 compliant), and Sun PC-NFS. Windows 95 has "dial-up networking" which supports Winsock and TCP/IP. winsock.dll is available from some TCP/IP stack vendors. Novell has one in beta for their Lan Workplace for DOS. Peter Tattam <peter@psychnet.psychol.utas.edu.au> is alpha-testing a shareware Windows Sockets compliant TCP/IP stack winsock/winsock.zip">ftp://ftp.utas.edu.au/pc/trumpet/winsock/winsock.zip. and winsock/winpkt.com">ftp://ftp.utas.edu.au/pc/trumpet/winsock/winpkt.com. {The Consummate Winsock App List (http://wwwvms.utexas.edu/Windows socketsNeuroses/cwsapps.html)}. [Adapted from: Aboba, Bernard D., comp.protocols.tcp-ip.ibmpc Frequently Asked Questions, 1993 Usenet: news:news.answers, ftp://netcom1.netcom.com/pub/mailcom/IBMTCP/]. [Current status?] (1996-06-20)

Wikipedia

Winsock

In computing, the Windows Sockets API (WSA), later shortened to Winsock, is an application programming interface (API) that defines how Windows network application software should access network services, especially TCP/IP. It defines a standard interface between a Windows TCP/IP client application (such as an FTP client or a web browser) and the underlying TCP/IP protocol stack. The nomenclature is based on the Berkeley sockets API used in BSD for communications between programs.